> "A product that does not understand its user is like a suit cut for someone else's body. Technically clothing, yes, but a humiliation nonetheless."
---
Before We Begin
I want you to read this slowly.
Not because it is complicated, but because it took me years to understand it, and I do not want you to spend the same unnecessary amount of time arriving at truths that I am handing to you right now, freely, so that you can get on with the actual work of becoming someone remarkable in this field.
You are at a stage in your career where your instincts are forming and your habits are hardening, and the choices you make now about how you work, not just what you produce, will determine almost everything about the designer you become.
So. Let us talk about what actually matters.
---
The Problem You Will Face, Probably Very Soon
You will be in rooms, where user experience is treated as an afterthought placed beside engineering and sales.
You will be the youngest person at the table, or close to it, and someone with a title will imply that your work is secondary. That UX is nice to have but there is not really time for it in this sprint, this quarter, this fiscal year.
I need you to understand that this is one of the most expensive mistakes an organization can make in the very real, very measurable sense of lost customers that occurs when people interact with something that was clearly never built with them in mind.
The real challenge ahead of you is not simply doing the work of UX. It is making others understand why that work matters, why it belongs at the table, why it deserves resources, attention, and the kind of organizational commitment that transforms a good product into an unforgettable one.
Nobody teaches you this in school. I am teaching you now.
---
Principles Over Processes. This Is Not Up for Debate.
Here is the first thing I want you to tattoo somewhere inside your mind: processes will shift, processes will be cut, reorganized, renamed, and handed off to someone who learned them from a two-day workshop. Principles, on the other hand, are immovable. They are the architecture beneath the architecture.
Early in your career, you will be tempted to lean heavily on process. On frameworks. On the reassuring structure of the particular methodology that your current company has adopted. I understand this temptation.
But if you anchor your work to principles you will retain your footing no matter how many times the organization decides to restructure itself. And they will restructure themselves. Frequently. Often right before a product review.
The principle is your foundation, while the process is merely the seasonal trend, here today and absolutely somewhere in a landfill by spring.
What this means practically is that you should enter every engagement not asking "what is our UX process?" but instead asking "what do we believe about the people who use this?"
Ask the human question first. Always.
---
The Four Principles I Have Built My Career On
I have used every single one of these in organizations that were resistant and skeptical. Use them.
I. Invite People In
The most powerful thing you can do as a designer, is make someone who is not a designer feel genuinely welcomed into the design process. Not as a courtesy. As a sincere expression of your belief that their presence enriches the work.
You will work with engineers who think in systems, product managers who think in roadmaps, executives who think in quarters. They are not your adversaries. They are your collaborators who have not yet been properly invited.
Bring them in. Show them the research sessions. Put a sticky note in their hand and watch something shift behind their eyes when they realize that they too have an opinion about users, that they too have been carrying assumptions about human behavior that were never tested.
This is how you build allies. Build them early, and build them everywhere.
II. Make Things Together
You will be tempted, especially when you are trying to prove yourself, to show up to every meeting with something polished, something finished.
Resist this.
There is something almost miraculous that happens when you put a rough sketch in front of a roomful of stakeholders who expected a polished presentation. The roughness gives people permission.
In those moments I have gotten more useful, more honest, more generative input than I ever would have received. Collaborative, imperfect creation is how real alignment is built through shared authorship.
Show your rough work, it is one of the most sophisticated things you can do in a room.
III. Truly Listen
This one is harder than it sounds, and I say that knowing you probably believe you are already a good listener.
Listening is not the passive act of remaining silent while someone else speaks. True listening is an athletic endeavor. It requires the sustained, disciplined, deeply uncomfortable practice of letting another person's perspective actually land inside you.
When a stakeholder expresses concern about your design direction, your instinct as a junior or mid-level designer will be to defend your work immediately. I know this feeling intimately.
Do not do this.
Instead, sit with their concern. Turn it over. Ask yourself whether it contains something you missed, something your own assumptions had blinded you to. More often than you will be comfortable admitting, it does.
This kind of listening, real listening that is willing to be changed, is how you build the relationships that will sustain your work through organizational turbulence.
In those moments, you will need the accumulated trust of months of genuine attention. You cannot manufacture it on demand. You build it now, in the ordinary moments, by being someone who actually listens.
IV. Know When It's Good Enough
~~Perfectionism~~ is not discipline. It is fear wearing a very well-tailored disguise.
the perfect design delivered too late or never delivered at all serves no one, least of all the users whose lives it was meant to improve.
The standard you should hold is not "is this perfect?" but rather "is this meaningfully better than what exists, does it solve the right problem in a way that is defensible, and can we learn from shipping it?"
Learn to have an ongoing, active dialogue with your stakeholders about what "good enough" means in a given context, for a given deadline, for a given level of risk.
This is not compromising your standards and it will earn you more organizational trust than a hundred perfect deliverables.
Ship the thing. Learn from it. Improve it. This is how the work actually moves forward.
---
On Relationships
the quality of your relationships will determine the ceiling of your UX impact. More than your craft. More than your portfolio.
Every practitioner I have watched build genuine, lasting influence in an organization has done it primarily through relationships. Not through superior outputs.
Invest in one-on-one conversations before you need them. Build informal networks across departments. Make your colleagues feel like collaborators rather than subjects of your research.
Conduct one-on-one interviews to give people the experience of being heard by someone who is paying attention. Involve colleagues in research sessions because they genuinely make the research better. They catch things you miss.
The collaborative session is both a design tool and a relationship tool simultaneously.
---
Two Things That Will Save You
Show Your Thinking Before It Is Final
One of the most consistently effective habits you can build, and I want you to build it now, is showing visual representations of requirements and ideas to stakeholders before those requirements have been fully agreed upon.
Nothing surfaces hidden assumptions more efficiently than watching someone react to a visualization with an expression that tells you they were imagining something entirely different.
Show things early. Show things rough. Show things often. Every time, the room becomes more honest, and honest rooms produce better products.
Document Everything You Win
Document your wins. Start now.
Because organizational memory is short and skepticism is long. The case study is how you keep the evidence of UX's value visible and retrievable in the moments when someone, somewhere begins to wonder whether all of this user-centered effort is really necessary.
Give them something to look at before they finish that thought. This is your responsibility. Nobody else will do it for you.
---
The Objections You Will Hear, and Exactly What to Say
You will face these. Here is how you respond.
> "UX is just making things pretty."
No. UX is the practice of understanding why people do what they do and designing systems that serve those behaviors, motivations, and mental models.
If beauty emerges from that process, as it often does, it is because clarity and coherence are inherently beautiful, not because aesthetics were the primary objective.
> "We already do market research, isn't that the same thing?"
Market research tells you what people say they want in a context specifically designed to elicit consumer responses. UX research observes what people actually do when they encounter your product in conditions that approximate real use.
The gap between those two datasets is often where your most important insights live.
> "We can't afford UX."
What you cannot afford is the cost of building something that does not work for the people it was built for. The rework, the support calls, the churn, the reputation damage, the competitive disadvantage of a product that frustrates rather than delights.
That is the actual financial comparison that deserves attention.
> "UX slows us down."
Early UX investment consistently reduces the expensive late-stage changes that occur when a product is nearly finished and someone finally watches a user attempt to use it with the specific expression of a person encountering a locked door they were certain would be open.
Memorize these. Refine them in your own voice. And never, ever apologize for asking that the user be considered.
---
What I Want You to Leave With
Advocacy for user-centered design is a practice you sustain indefinitely, and it will be asked of you at every stage of your career, not just at senior level.
Understand that organizational politics is not something that's beneath the dignity of a designer.
The work is never finished. That is the nature of a living practice.
Carry these principles with you. Express them constantly, in everything from the language you use in meetings to the way you frame a research finding.
user-centered design is not a methodology. It is a moral position. And the designers who understand this, who live this, are the ones whose work endures and whose influence compounds over time.
You are at the beginning of something. Make it count.
---
Because in the end, everything, every product, every interface, every interaction, is a statement about what you think of the person on the other side of it.
Make it a generous one.
---